fix: remove privacy page#4794
Merged
Trott merged 2 commits intonodejs:mainfrom Aug 24, 2022
Merged
Conversation
The privacy policy for the OpenJS Foundation is linked in the footer. We do not need to maintain a separate privacy page.
ghost
approved these changes
Aug 24, 2022
Member
|
/Is it worth doing a redirect in the build repo? |
Member
Should we do the same for nodejs.dev? |
Member
Author
Ideally, yes! |
Member
Author
I would say yes. |
Member
|
Think the redirects go in https://github.com/nodejs/build/blob/bfdea82300d635fcac681656885d7b7736ee62a3/ansible/www-standalone/resources/config/nodejs.org, although that page seems to confuse the GitHub previewer 😆 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The privacy policy for the OpenJS Foundation is linked in the footer.
We do not need to maintain a separate privacy page.